Changed the cache entry save strategy from find-first-then-update-or-create to create-first-then-handle-unique-violation. This approach better handles concurrent requests where multiple instances might attempt to create the same cache entry simultaneously. By catching unique constraint violations and falling back to find-and-update, we prevent duplicate entries and ensure data consistency while maintaining the original caching behavior.